Privacy policy

        Last updated: 29 July 2026
        See what changed
      

The short version

—We don't use your meetings to train AI models. Not now, not later, not in aggregate.

—MeetWork appears in the participant list. It never joins silently.

—You choose how long meetings are kept. You can delete one the moment it ends.

—You can get everything we hold about you, or have it erased, from your account settings.

The full policy below is the binding version.

1. Who we are and how to reach us

MeetWork is operated by MeetWork Inc. For any question about this policy, or to exercise a privacy right, write to privacy@meetwork.example. Customers in the EU and UK can reach our representative at the same address; we will route the request.

2. What this policy covers

This policy covers our website, our product, and the meetings MeetWork joins. Website cookies are covered by the cookie policy and by the preferences you set in the consent banner; those settings never govern meeting data.

3. Information we collect

Account data you give us: name, work email, workspace, billing details. Calendar metadata needed to join the right meeting: title, time, participant list.

Meeting data produced while MeetWork is present: audio it processes to interpret, transcripts, summaries, and action items. Plus ordinary technical logs: device, IP, and error traces.

4. How we use it

To interpret speech, produce recaps, route action items to the tools you connect, keep your account secure, bill you, and support you. Nothing else.

5. Legal bases for processing (GDPR)

Performance of a contract for the core service; legitimate interests for security and service reliability; consent where consent is required, including for voice characteristics; legal obligation where the law compels us.

6. Who we share it with

Subprocessors that host our infrastructure and perform interpretation and summarization, each under contract. The tools you choose to connect, such as Slack, Notion, or Jira, receive only what you route to them. We do not sell personal data.

7. International transfers

Meetings can be pinned to a processing region. Where data leaves that region, we rely on Standard Contractual Clauses or an equivalent transfer mechanism, and we document it in our DPA.

8. How long we keep it

Retention is set per workspace by its admin, and can be as short as deletion the moment the meeting ends. Account and billing records are kept as long as the law requires. When retention lapses, we delete; backups age out on a documented cycle.

9. Your rights and how to exercise them

Access, correction, deletion, portability, objection, and withdrawal of consent. Signed-in users can export or delete from account settings. Anyone else can write to privacy@meetwork.example; we respond within 30 days and never charge for a first request.

10. Security

Encryption in transit and at rest, least-privilege internal access with audit logging, annual penetration testing, and SOC 2 Type II controls. Our security overview describes the details.

11. Children

MeetWork is a workplace product and is not intended for anyone under 16. We do not knowingly collect their data, and we delete it if we learn we have.

12. Changes to this policy

We keep a public change history. For material changes we notify workspace admins by email at least 30 days before they take effect.

13. Meeting participants who aren't our customers

MeetWork is added to a meeting by one participant — our customer. Other people in that meeting may never have visited our site or agreed to our terms. We still process their voice, their words, and their name as it appears in the meeting.

Here's how we handle that:

—MeetWork joins as a visible, labelled participant. It is never hidden or disguised as a person.

—The customer who added it is the controller of that meeting's data. We act as their processor. Requests to delete or access a meeting normally go to them, but you can contact us directly at privacy@meetwork.example and we will help.

—If you're in a meeting and you don't want MeetWork there, you can say so and any participant can remove it. We also publish a page explaining what MeetWork is, formeeting participants.

—We don't build profiles of meeting participants. We don't use a participant's data to market to them, and we don't link their voice across meetings from different customers.

14. Recording, interpretation, and consent

Laws about recording conversations differ by country and, in the United States, by state. Some require every participant to consent, not just the person who started the recording.

—MeetWork announces itself when it joins and remains visible in the participant list for the whole meeting.

—Workspace admins can require a spoken or written consent notice at the start of every meeting.

—The customer who adds MeetWork is responsible for having the right to record and interpret that meeting under the laws that apply to them and to the other participants. Our tools help; they don't transfer that responsibility to us.

If you believe a meeting was recorded without proper consent, contact privacy@meetwork.example.

15. Voice characteristics

Some MeetWork features analyze how you sound in order to make interpretation feel natural — for example, keeping the interpreted voice close to your own tone and pace.

Depending on where you live, this may count as biometric information under laws such as the Illinois Biometric Information Privacy Act. Where that's the case:

—We ask for your explicit, separate consent before turning the feature on. It is off by default.

—We tell you how long we keep the derived voice data and when we destroy it.

—We never sell, lease, or trade it, and we don't use it to identify you across meetings.

—You can withdraw consent at any time in your account settings, and we delete the derived data.

16. How we use meeting data with AI models

—We do not use your meetings — audio, transcripts, summaries, or action items — to train our own models or anyone else's.

—We use third-party AI providers to perform interpretation and summarization. We contract with them so that your content is not retained beyond what's needed to return a result, and is not used for their training.

—We publish the list of subprocessors we use, and give notice before adding a new one.

—Aggregate, non-identifying operational metrics (for example, average latency by language pair) may be used to improve the service. These contain no meeting content.

Cookie policy Subprocessors Security overview